Add new test case for equal boolean field #277
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexander-schranz
force-pushed
the
bugfix/boolean-equal-filter
branch
2 times, most recently
from
ad3fb35 to
ad41cb4
Compare
alexander-schranz
force-pushed
the
bugfix/boolean-equal-filter
branch
from
ad41cb4 to
f99c0d0
Compare
1 task
alexander-schranz
merged commit aec204b
into
PHP-CMSIG:bugfix/boolean-filter
18 of 32 checks passed
alexander-schranz
added
features
|
Merging this into an own branch bugfix/boolean-filter which will be used as target branch for collect all Pull Requests for fixing the boolean filters. |
This was referenced Nov 12, 2023
alexander-schranz
added a commit
that referenced
this pull request
Nov 12, 2023
alexander-schranz
added a commit
that referenced
this pull request
Nov 12, 2023
alexander-schranz
added a commit
that referenced
this pull request
Nov 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
See #276